Description

In handle_case, the exception message is printed through Rich with markup parsing enabled, so
exception strings containing [/] can be interpreted as markup and raise a Rich rendering error
while reporting the failure. This can interrupt the test runner’s failure reporting and hide the
original test error.

Code

toolchain/mfc/test/test.py[614]

+            cons.print(f"    Error: {exc}")

Evidence

cons ultimately prints via rich.console.Console.print() with no markup=False or escaping, so
arbitrary exception text is treated as Rich markup. handle_case prints {exc} on failure, and
test execution uses subprocess.run via common.system, which can surface non-MFC exceptions whose
string form may include bracketed segments that are unsafe under markup parsing.

toolchain/mfc/test/test.py[602-618]
toolchain/mfc/printer.py[7-40]
toolchain/mfc/common.py[62-70]
toolchain/mfc/test/case.py[166-187]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`handle_case` prints exception text via Rich markup parsing. If the exception message contains `[` / `]` sequences, Rich may interpret them as markup and raise during printing, masking the original test failure.

## Issue Context
The printer wrapper uses `rich.console.Console()` and forwards strings to `Console.print()` without escaping, so markup parsing is on by default.

## Fix Focus Areas
- toolchain/mfc/test/test.py[609-616]
- toolchain/mfc/printer.py[7-40]

## Suggested change
Print the error line with markup disabled (or escape the exception text). For example:
- `cons.print(f"    Error: {exc}", markup=False)`

Optionally preserve formatting for your own exceptions only:
- `cons.print(f"    Error: {exc}", markup=isinstance(exc, MFCException))`
(or escape only when not an `MFCException`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Walkthrough

The change modifies how exceptions are displayed in error output. Previously, exception strings were explicitly truncated to 300 characters before being printed. The update removes this truncation logic and instead prints the full exception object directly. The exception string is still converted to lowercase and used for hint logic and error categorization downstream, so the control flow and decision-making remain unchanged—only the display formatting behavior is altered.

• X
• Mastodon
• Reddit
• LinkedIn

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.